home *** CD-ROM | disk | FTP | other *** search
- Path: gaia.ns.utk.edu!mbk
- From: mbk@caffeine.engr.utk.edu (Matt Kennel)
- Newsgroups: comp.object,comp.lang.c++,comp.lang.java
- Subject: Re: Java: What's the Big Deal?
- Followup-To: comp.object,comp.lang.c++,comp.lang.java
- Date: 21 Mar 1996 21:56:37 GMT
- Organization: University of Tennessee, Knoxville and Oak Ridge National Laboratory
- Message-ID: <4isjal$4pe@gaia.ns.utk.edu>
- References: <4i40ik$9dt@news4.digex.net> <milodDo5yDE.H8B@netcom.com> <314B8239.247D@netalive.com> <slrn4knlcc.avu.johnm@mitchell.org> <314DD247.532F@netalive.com>
- Reply-To: kennel@msr.epm.ornl.gov
- NNTP-Posting-Host: caffeine.engr.utk.edu
- X-Newsreader: TIN [version 1.2 PL2]
-
- Erik P. DeBenedictis (erikd@netalive.com) wrote:
- : I will try to make this a thoughtful reply.
-
- : Remember, this thread is called "Java: What's the Big Deal."
-
- : The idea of making a language internally secure (to catch accesses off
- : the end of an array, etc.) has been around for a long time. Java has a
- : fairly unique way of doing this. However, it's a "little deal."
-
- : The idea of putting functions (or applications) on Web pages so they can
- : be accessed by the public, but without the possibility of introducing
- : Trojan Horses or viruses, is much newer. I believe this is a "Big Deal."
- : However, Java's secure bytecode is not the only way to do this.
-
- Of course not. But they did it.
-
- Making a conventional 'safe' language that doesn't crash from bad array
- bounds is old news, but that's only subset---admittedly vital---of what
- has to be done and thought about to really prevent viruses and trojans.
-
- That part is newer.
-
-